Device management system with a restore prevention utility

ABSTRACT

In various embodiments, methods and systems for implementing a device management system with a restore prevention utility are provided. A request is received, at a control server, for an installation file for a restore prevention application. Based on receiving the request, the control server circumvents communication of the installation file based on transmitting a response code. The response code is an informational code that operates as an indicator to wait for a final response. Transmitting the response code triggers maintaining a pending state for the restore prevention application at the controlled device. The pending state includes the restore prevention application partially installed such that when the restore prevention application is partially installed an operating system cleanup utility operation to restore default device configurations for arranging application icons on the controlled device, is circumvented, to maintain an existing device configuration for arranging application icons on the controlled device.

BACKGROUND

An operating system cleanup utility operates to maintain proper statesand functioning of installed system files, applications and servicesrunning on the operating system. The operating system cleanup utilitycan be included in a variety of devices including media platforms fromvideo game systems and television systems to mobile devices and personalcomputers. Implementing and managing third party applications andservices for devices that include operating system cleanup utilities canbe challenging when the operating system cleanup utility is designed toaggressively maintain specific states for third party applications andservices. Third party applications and services may need to operatebased on states that are contrary to the operating system cleanuputility objectives. Circumventing such operating system cleanup utilityobjectives can be achieved using specific configurations, operations andcomponents associated with the operation of the third party applicationsand services.

SUMMARY

Embodiments of the present invention provide methods and systems forimplementing a device management system with a restore preventionutility. A device management system, via a device management manager,supports the administration of one or more mobile devices for thirdparty applications and services. The device management managercommunicates a device management package to a mobile device to initiatethe installation process of a restore prevention application. The devicemanagement package includes configuration files for configuring devicemanagement on the mobile device. The device management manager receivesa request for an installation file for the restore preventionapplication. Based on receiving the request for the installation file,the device management manager circumvents communication of theinstallation file based on transmitting a response code. The responsecode is an informational code that operates as an indicator for themobile device to wait for a final response, where the response code is aresponse code that is not ignored. As such, the response code causes anoperating system cleanup utility not to proceed with terminating theinstallation process of the restore prevention application. The responsecode can specifically be unidentified or excluded from a list ofresponse codes that cause an operating system cleanup utility to proceedwith terminating the installation process of the restore preventionapplication on the mobile device.

Transmitting the response code triggers maintaining a pending state forthe restore prevention application in the installation process at themobile. The pending state includes the restore prevention applicationpartially installed at the mobile device. When the restore preventionapplication is only partially installed, an operating system cleanuputility operation to restore default device configurations, forarranging application icons on the mobile device, is circumvented, tomaintain an existing device configuration for arranging applicationicons on the mobile device.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used in isolation as an aid in determining the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary device management system inwhich embodiments described herein may be employed;

FIG. 2 is an schematic showing functional components performing anexemplary method for implementing a device management system with arestore prevention utility, in accordance with embodiments describedherein;

FIG. 3 is a flow diagram showing an exemplary method for implementing adevice management system with a restore prevention utility, inaccordance with embodiments described herein;

FIG. 4 is a flow diagram showing an exemplary method for implementing adevice management system with a restore prevention utility, inaccordance with embodiments described herein;

FIG. 5 is a flow diagram showing an exemplary method for implementing adevice management system with a restore prevention utility, inaccordance with embodiments described herein; and

FIG. 6 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments described herein.

DETAILED DESCRIPTION

An operating system cleanup utility operates to maintain proper statesand functioning of installed system files, applications and servicesrunning on the operating system. The operating system cleanup utilitycan be included in a variety of devices including media platforms fromvideo game systems and television systems to mobile devices and personalcomputers. Implementing and managing third party applications andservices for devices that include operating system cleanup utilities canbe challenging when the operating system cleanup utility is designed toaggressively maintain specific states for third party applications andservices.

By way of background, third party products can be maintained based ondevice management systems having a device management tool (e.g., mobiledevice management system “MDM”). A device management tool can supportadministration of devices, such as, media platforms (e.g., video gamesystems, smart televisions) or mobile devices (e.g., smartphones,tablets, laptop computers). The device management tool can be leveragedto implement features and enforce policies on the devices. For example,a device management tool can be used to implement controls (e.g.,content controls, application controls and usage controls) and restrictaccess to content. In operation, the device management system runningthe device management tool can include a control server component (e.g.,device management manager) that sends out management commands to acontrolled device (e.g., a mobile device) having a controlled devicecomponent (e.g., device management client application) which runs on thecontrolled device to receive and implement the management commands.

Third party applications and services operate based on device managementcommands and operations which trigger predefined operations of anoperating system cleanup utility. For example, the device managementmanager can instruct a mobile device to operate in a restricted mode,such that, the device management manager can implement restrictions andcontrols (e.g., settings of restriction profile). The restricted modecan be initiated at the mobile device having the device managementclient application. The restricted mode can be initialized based ontransmitting a restriction profile from the device management manager tothe mobile device. With the restricted mode initialized, the restrictionsettings (e.g., disable or hide icons of one or more applications on themobile device) can be implemented at the mobile device. The restrictedmode can be terminated when the device management manager disables orremoves the restriction profile.

Terminating the restricted mode is associated with a set of restoreoperations performed by the operating system cleanup utility, where theset of restore operations include restoring default deviceconfigurations. For example, restoring default device configurations caninclude restoring application icons to default device configurations forthe application icons (e.g., restoring application icons in alphabeticalorder or a predefined configuration). Restoring the default deviceconfiguration for the application icons removes an existing deviceconfiguration for the applications icons. For example, existing folderhierarchies for folders and subfolders and arrangement of applicationicons are replaced, upon terminating the restricted mode, with thedefault device configuration for the application icons. Losingpreviously existing device configurations, especially folder hierarchiesfor folders and subfolder and arrangement of application icons can beburdensome to users who then have to reconfigure their user-defineddevice configurations (e.g., re-arrange application icons). Moreover,the operating system cleanup utility operations can be particularlyoppressive when a third party application operates only periodically toinitialize and terminate the restricted mode which in turn triggersrestoring the default device configuration each time the restricted modeis terminated.

Third party applications and services may need to operate based onparticular states to support functionality of the third partyapplications and services; however such states can be contrary to theoperating system cleanup utility objectives. Circumventing suchoperating system cleanup utility objectives to restore default deviceconfiguration, in particular upon terminating a restricted mode, can beachieved using specific configurations, operations and componentsassociated with the operation of the third party applications andservices. As such, a comprehensive device management system thatsupports circumventing cleanup utility operations can help maintainthird party applications and services in states preferred by the thirdparty developers.

Embodiments of the present invention provide simple and efficientmethods, and systems, for implementing a device management system with arestore prevention utility. At a high level, the device managementsystem implements a restore prevention application on a device having anoperating system cleanup utility that operates to restore default deviceconfigurations. In particular, using the restore prevention application,the device management system circumvents the operating system cleanuputility's capacity to the restore default device configurations on thedevice. Circumventing the operating system cleanup utility is based onmaintaining the restore prevention application in a pending state of theinstallation process, in that, while the restore prevention applicationis in the pending state, the restore prevention application is onlypartially installed on the device and the operating system cleanuputility does not proceed with restoring default device configurations.Advantageously, the device management system can implement devicemanagement functionality on the device while maintaining existing deviceconfigurations which would otherwise be overwritten by the operatingsystem cleanup unity.

Embodiments of the device management system with a restore preventionutility can be described based on a specific exemplary implementation.The features of the embodiments described below are meant to beexemplary and not intended to limit the scope of the invention, unlessotherwise stated. A mobile device (i.e., a controlled device) that ismanaged for implementing parental controls and restrict resourcerequests (i.e., device restrictions and controls) on the mobile devicecan be part of the device management system. The mobile device ismanaged using a device management server (i.e., control server) runningon device management manager (i.e., control server component) tofacilitate mobile device management of the mobile device. In particular,the device management manager controls the mobile device based on adevice management payload (i.e., device management package) that refersto a set of files that are transmitted to the mobile device to configurethe mobile device for device management. The device management payloadcan include configuration files for a device management clientapplication (i.e., a controlled device component), the restoreprevention application, and a restriction profile. It is contemplatedthat the configuration files can include instructions on how and whereto retrieve one or more installation files for installing the devicemanagement client application, the restore prevention application, andthe restriction profile. Other variations and combinations of devicemanagement payloads and transmitting device management payloads arecontemplated with embodiments of the present disclosure.

The device management client application supports implementing controlson the mobile device, the restore prevention application supportscircumventing restoration of default configurations of the mobiledevice, and the restriction profile file includes restriction profilesettings for controlling the mobile device. In one exemplaryimplementation, the device management system along with devicemanagement client application, the restore prevention application, and arestriction profile can support a VPN-based parental control servicecorresponding to the VPN-based parental control service described inU.S. application Ser. No. 15/159,584, entitled “VIRTUAL PRIVATE NETWORKBASED PARENTAL CONTROL SERVICE WITH MOTION-BASED RESTRICTION”,incorporated herein by reference in its entirety.

In operation, the mobile device can be enrolled to be managed via thedevice management system. The device management payload can becommunicated to the mobile device, where the device management clientapplication is installed. The restore prevention application can beinitialized during part of the installation process but then maintainedin a pending state. In one exemplary embodiment, initializing therestore prevention application can include accessing the configurationfiles in the device management payload. The configuration files instructthe mobile device (e.g., operating system—iOS 10 or greater by developerAPPLE Inc.) to sequentially request (e.g., via the device managementmanager or a host server) corresponding files of an installation package(e.g., a property list file and corresponding archive installer file).The property list file (i.e., .plist file) can be retrieved, where theproperty file operates to trigger the installation process for therestore prevention application. The property list file can also instructon a location (e.g., device management manager or a host server) of thecorresponding archive installer file (i.e., .ipa file) that can beretrieved during the installation process to complete the installationof the restore prevention application.

The mobile device (e.g., via the operating system or the devicemanagement application) can request the archive installer filecorresponding to the property list file for the restore preventionapplication to complete the restore prevention application. While thearchive installer file is being retrieved, the restore preventionapplication is in a pending state of the installation process and if thearchive installer file is not received, an operating system cleanuputility that operates to maintain specific states for applications willterminate the installation process and remove the restore preventionapplication from a pending state (i.e., installing state) to anot-installed state.

Embodiments of the present invention operate to maintain the restoreprevention application in the pending state of the installation process,where the pending state includes the restore prevention application onlypartially installed on the device. As such, the operating system cleanuputility does not proceed with restoring default device configurations.In other words, when the restore prevention application is in thepending state, the operating system cleanup utility operations arecircumvented. In particular, the operating system cleanup utility'scapacity or logic to restore default device configurations to overwriteexisting device configurations is paused or broken when the restoreprevention application is the pending state.

As discussed, during the installation process for installing the restoreprevention application, a request is transmitted to retrieve the archiveinstaller file for the restore prevention application. When the requestis received, for example at the device management manager, communicatingthe archive installer file is circumvented and instead a response codeis communicated such that the restore prevention applicationinstallation process is paused and the restore prevention application ismaintained in the pending state. In particular, maintaining the restoreprevention in the pending state is based on receiving, a response codein response to the request for the archive installer file. The responsecode is an informational code that operates as an indicator for themobile device to wait for a final response. The response code is notignored, such that, it is at least a cause of an operating systemcleanup utility not to proceed with terminating the installation processof the restore prevention application. The response code can be excludedfrom a list of response codes that cause an operating system cleanuputility to proceed with terminating the installation process of therestore prevention application on the mobile device. Typically,unsuccessful response codes are actioned (e.g., during installation)causing the operating system cleanup utility to proceed with terminatingthe installation process.

The response code can be specifically defined with some variations asdescribed in examples below. For example, the response code can be aninformational response code that alerts the operating system to wait fora final response. In this regard, the response code can be a checkpointor standby code. An informational response indicates that the requestwas received and understood. The informational response is issued on aprovisional basis seemingly to indicate that the request processingcontinues. In one exemplary embodiment, the response code can be astandard Hypertext Transfer Protocol (e.g., HTTP 103 Checkpointresponse). The response code may consist only of the status line andoptional header fields, and is terminated by an empty line.

It is further contemplated that the response code may be intentionallyor unintentionally excluded from the list of response codes. Theresponse code can be a code that communicates an indication that a hostof the archive installer exists, but there exists a delay intransmitting the archive installer file. The response code can also be acode that the operating system (e.g., mobile operating system) has noprogrammed response for, such that, the response code prevents theoperating system cleanup utility from proceeding with terminating theinstallation process of the restore prevention application. The responsecode may also be a code which the operating system cleanup utility isnot explicitly programmed to ignore and then proceed with terminatingthe installation process of the restore prevention application. Othervariations and combination of response codes that are unidentified orexcluded from a list of response codes that cause the operating systemcleanup utility to proceed with terminating the installation process ofthe restore prevention application are contemplated with embodimentsdescribed herein.

In operation, the response code can be transmitted to the mobile deviceand the operating system cleanup utility does not terminate theinstallation process. In one embodiment, the operating system cleanuputility at least provides an extended period (i.e., not immediately)including several hours, days, weeks or years, for not terminating theinstallation process and the restore prevention application remains inthe pending state or installing state. Advantageously, as the restoreprevention application is maintained in the pending state and theinstallation process is not terminated, the operating system cleanuputility does not proceed with restoring the default device configurationwhen the restricted mode is terminated. For example, a restricted modecan include disabling applications or hiding the application icons;however, when the restricted mode is terminated, the application iconsare not restored to a default device configuration for the applicationicons (e.g., an alphabetic or predefined arrangement) instead theexisting device configuration, (e.g., a user-defined arrangement ofapplication icons) prior to initializing the restricted mode, ismaintained on the mobile device.

In one embodiment, the device management system implements a recoverysolution having recovery operations for the restore preventionapplication pending state. Specifically, the recovery solutionidentifies that the restore prevention application is no longer in thepending state and then proceeds with recovery operations thatre-initialize the restore prevention application in the pending state.The recovery solution includes the device management manager at leastperiodically querying the mobile device for a status of the restoreprevention application. A status request is transmitted to the mobiledevice and the mobile device then communicates a status response. Themobile device can transmit a status response which indicates that therestore application is still in the pending state (e.g., “managedapp—installing”) which results in no further action on the part of thedevice management manager.

The mobile device can, in the alternative, transmit a status responsewhich indicates that the restore application is not in a pending state(e.g., “managed app—not installed”). The recovery operations can beimplemented in several different ways in order to re-initialize therestore prevention application. For example, the user can be notified tore-install the restore prevention application which includes the mobiledevice sequentially requesting corresponding files of an installationpackage (e.g., a .plist file and corresponding .ipa files). The devicemanagement manager can automatically push the property file causing themobile device to request the archive installer file. In either case, themobile device eventually requests the archive installer file, whichresults in the device management manager circumventing communicating thearchive installer file based on communicating a response code. Themobile device receives the response code and the restore preventionapplication installation process is paused and the restore preventionapplication is maintained in a pending state.

As discussed, when the restore prevention application is in the pendingstate the operating system cleanup utility operations are circumvented.In particular, the operating system cleanup utility's capacity or logicto restore default device configurations to overwrite existing deviceconfigurations is paused or broken when the restore preventionapplication is in the pending state. In this regard, advantageously, auser of the mobile device does not have to reconfigure theiruser-defined device configurations each time the restricted mode isinitiated and terminated.

With reference to FIG. 1, FIG. 1 illustrates an exemplary devicemanagement system with a restore prevention utility (“device managementsystem” 100) in which implementations of the present disclosure may beemployed. In particular, FIG. 1 shows a high level architecture ofdevice management system 100 having components in accordance withimplementations of the present disclosure. It should be understood thatthis and other arrangements described herein are set forth only asexamples. In addition, a system, as used herein, refers to any device,process, or service or combination thereof. A system may be implementedusing components as hardware, software, firmware, a special-purposedevice, or any combination thereof. A system may be integrated into asingle device or it may be distributed over multiple devices. Thevarious components of a system may be co-located or distributed. Forexample, although discussed for clarity as the controller server,operations discussed can be performed in a distributed manner via adistributed device management manager service (not shown) running oncomputing devices in a distributed manner. The system may be formed fromother systems and components thereof. It should be understood that thisand other arrangements described herein are set forth only as examples.

Among other components not shown, device management system 100 includesa control server 110 having a control server component 112, a controlleddevice having a controlled device component 122, an operating system124, an operating system cleanup utility 126, a restore preventionapplication 128 and a network 130. The components of the devicemanagement system 100 may communicate with each other over one or morenetworks (e.g., public network or virtual private network “VPN”). Thenetwork 140 may include, without limitation, one or more local areanetworks (LANs) and/or wide area networks (WANs). Any number of nodes(e.g., servers) and client computing devices may be employed within thedevice management system 100 within the scope of implementations of thepresent disclosure.

The components of the device management system 100 can be implemented incombination to provide the functionality of the device management systemdescribed herein. Specifically, the control server 110 is responsiblefor implementing device management of the controlled device. The devicemanagement system 100 can include the control server 110 (e.g., a mobiledevice management “MDM” tool) that administers mobile devices running amobile operating system. In particular, the control server 110 caninclude the control server component 112 (e.g., a device managementmanager) for performing operations of the control server 110 describedherein. The control server 110 can operate as a store for files used forimplementing embodiments described herein. For example, the controlserver 110 can store and transmit the device management package and alsohost and transmit the installation package for the restore preventionapplication. Alternatively, the control server 110 can instruct on alocation for accessing the device management package and theinstallation package.

The control server 110 operates to communicate commands, messages, andfiles that facilitate maintaining a restore prevention application onthe controlled device 120 in a pending state of an installation processin order to circumvent an operating system cleanup utility's capacity torestore default device configurations. The control server 110 canreceive a request for an archive installer file for the restoreprevention application and respond with a response code that iscommunicated, such that, the restore prevention application installationprocess is paused and the restore prevention application is maintainedin the pending state. In embodiments, the control server 110 alsoimplements a recovery solution that identifies that the restoreprevention application is no longer in the pending state and thenperforms recovery operations that re-initialize the restore preventionapplication in the pending state.

The controlled device 120 operates based on instructions from thecontrol server 110 and includes several components that support devicemanagement functionality on the controlled device 120. The controlleddevice 120 can be a computing device with components and featuresdescribed with reference to the computing device in FIG. 6. Thecontrolled device 120 can be a mobile device with a mobile operatingsystem. The controlled device 120 includes a controlled device component122 (e.g., device management client application) that facilitatesimplementing device management restrictions and controls. For example,the controlled device can transmit messages to enroll in devicemanagement and receive a device management package, as described herein.

The controlled device component 122 operates to receive commands fromthe control server component 112 via the control server 110 to implementrestrictions and controls on the controlled device 120. For example, thecontrol server component 112 can request to initialize and terminate arestricted mode on the controlled device 120 based on communicating oneor more messages or commands to the controlled device component 122 toinitialize and terminate the restricted mode. The controlled devicecomponent 120 can also receive a request for a status of one or moremanaged applications of the device management system and communicate acorresponding status of the one or more applications. Other variationsand combination of device management operations performed using thecontrolled device component 122 are contemplated with embodiments ofdescribed herein.

The controlled device 120 includes an operating system 124 and operatingsystem cleanup utility 126. The operating system 124 supports performingoperations on the controlled device including installing applications,requesting installation files, and communicating the status informationreceived via the controlled device component 122. The operating systemcleanup utility 126 can be a portion of an operating system of themobile device or an independent utility configured to maintain systemfiles, applications and services in predefined states. In particular,the operating system cleanup utility 126 can be defined to restoredefault device configurations (e.g., application icons in alphabeticalorder) upon termination of a restricted mode at the controlled device120.

The operating system 124, in combination with the operating systemcleanup utility, can perform operations that are exploited to have therestore prevention application operate in a pending state. For example,the operating system having the operating system cleanup utility can beconfigured to understand response codes that are transmitted during aninstallation process of an application on the controlled device 120. Theoperating system can understand the response code as an informationalcode that operates as an indicator for the operating system to wait fora final response. The response code is not ignored or not processed,such that, the response code causes the operating system and theoperating system cleanup utility not to proceed with terminating theinstallation process of the restore prevention application. Theoperating system may also maintain a list response codes that causeoperating system cleanup utility to proceed with terminating theinstallation process of the restore prevention application. As such,upon requesting an archive installer file and receiving theinformational response code that is successful and not actionable byproceeding with terminating the installation process, the operatingsystem instructs the operating system cleanup utility to not proceedwith terminating the installation process and maintains the applicationin a pending state.

The controlled device 120 can further include a restore preventionapplication 128. The restore prevention application 128 is maintained ina pending state for restore prevention application in an installationprocess in order to circumvent the operating system cleanup utility'scapacity to restore default device configurations. In particular, therestore prevention application can include at least a portion of aninstallation package (e.g., a property list file) that initiates theinstallation process of the restore prevention application, includinggenerating an application icon for the restore prevention application128. A second portion of the installation package (e.g., an archiveinstaller file) can be requested but the portion of the installationpackage is not received. A response code is received instead, forexample via the operating system 124, where the response code operatesto pause the installation process of the restore prevention application,such that, the restore prevention application is maintained in thepending state. In particular, maintaining the restore prevention in thepending state is based on circumventing communicating the archiveinstaller file by communicating the response code, described herein.When the restore prevention application is in the pending state, theoperating system cleanup utility operations are circumvented.

It is contemplated that the restore prevention application operatesbased on a restore prevention application agent (not shown) thatsupports maintaining the status of the restore prevention application inthe pending state. For example, the device management package, theoperating system, or the restore prevention application installationpackage can include a restore prevention application agent that managesthe installation process for the restore prevention application. Therestore prevention application agent can process configuration files orinstallation files as part of the installation process for the restoreprevention agent. In this regard, the restore prevention applicationagent can support performing installation operations. In particular, therestore prevention agent can support maintaining a record that therestore prevention application is in a pending state. The restoreprevention application, via the restore prevention application agent,can also operate with the operating system for maintaining a record ofthe current status of the restore prevention application in the pendingstate. Other variations and combinations of a restore preventionapplication agent and/or an operating system managing the installationprocess to maintain a record of the restore prevention application inthe pending state are contemplated with embodiments described herein.

Turning to FIG. 2, FIG. 2 illustrates a schematic of exemplaryfunctional components and files, messages and commands communicatedbetween the functional components of the device management system toimplement the restore prevention utility. As shown, components describedwith reference to FIG. 2 are consistent with their correspondingdepicted components in FIG. 2. FIG. 2 includes control server 110 andcontrolled device 120 and corresponding components therein (e.g.,control server component, controlled device component, operating system,operating system cleanup utility, restore prevention application—notshown in FIG. 2). It is contemplated that the depicted individual stepscan include several additional actions not explicitly depicted in aparticular individual step.

Initially at step 222, a message can be communicated from the controlleddevice (e.g., from the operating system 124) to the control server 110requesting enrollment of the controlled device 120 for device managementvia the control server 110. At step 224, based on receiving theenrollment request from the controlled device 120, the control server110 can initiate enrollment of the controlled device 120. Initiatingenrollment of the controlled device can include several operationsincluding communicating a device management package including a set offiles that are transmitted to the controlled device 120 to configure thecontrolled device 120 for device management. The device managementpackage can include configuration files for installing a controlleddevice component 122 and a restore prevention application 128 on thecontrolled device 120. It is contemplated the control server 110 mayalso independently initiate enrollment of the controlled device basedpreviously defined configuration that provides the control server 110(e.g., control device component 122) access to the controlled device120.

At step 226, the controlled device 120 executes operations to enroll thecontrolled device. Enrolling the controlled device 120 can includeinstalling the controlled device component 122 on the controlled device.Enrolling the controlled device 120 can further include installing therestore prevention application on the controlled device 120. Installingthe restore prevention application can specifically include sequentiallyrequesting portions of an installation package of the restore preventionapplication. A property file of the installation package can beretrieved to initiate the installation process including preliminaryconfigurations and generating an application icon. The property file caninstruct on retrieving a second portion of the installation package ofthe restore prevention application. The second portion can be an archiveinstaller file.

At step 228, the controlled device 120 requests the installationfile—the archive installer file—from the control server 110. At step230, the control server 110 (e.g., the control server component 112 or ahost of the archive installer file) transmits a response code to thecontrolled device 120. At step 232, the controlled device 120 (e.g.,operating system 124) receives the response code, where the operatingsystem processes the response code The response code can be aninformational response code that alerts the operating system to wait fora final response. As such, the installation process is paused and therestore prevention application is maintained in a pending state.

At step 234, the control server 110 can request to initialize thecontrolled device 120 in a restricted mode. The control server 110 canspecifically communicate a restriction profile that is transmitted to,and implemented at, the controlled device. At step 236, the controlleddevice 120 (e.g., via the controlled device component 112) initializesthe restricted mode using the restriction profile and operates in therestricted mode. The restriction profile can specifically includedisabling or hiding applications and application icons during therestricted mode. At step 238, the control server 110 can request toterminate the restricted mode on the controlled device 120. The controlserver 110 can specifically instruct the controlled device 120 todisable or remove the restriction profile. Terminating the restrictedmode on the controlled device can trigger an operating system cleanuputility to restore default device configurations.

At step 240, the operating system cleanup utility restoration of thedefault device configuration is circumvented. In particular, theoperating system cleanup utility's capacity or logic to restore defaultdevice configurations to overwrite existing device configurations (i.e.,existing device configurations prior to initializing the restrictedmode) is paused or broken when the restore prevention application is inthe pending state. As such, for example, the arrangement of applicationicons prior to initializing the restricted mode is maintained and notoverwritten with a default alphabetical arrangement of applicationicons.

As previously discussed, the device management system implements arecovery solution having recovery operations for the restore preventionapplication. Specifically, the recovery solution identifies that therestore prevention application is no longer in the pending state andperforms and then proceeds with recovery operations that re-initializethe restore prevention application in the pending state. The recoverysolution includes the control server 110 at least periodically queryingthe mobile device for a status of the restore prevention application.

Accordingly, at step 242, the control server 110 can transmit a statusrequest from the controlled device 120. At step 244, the controlleddevice 120 can transmit a status response to the control server 110. Thecontrolled device 120 can transmit a status response which indicatesthat the restore application is still in the pending state (e.g.,“managed app—installing”) which results in no further action on the partof the control server. The controlled device 120 can, in thealternative, transmit a status response which indicates that the restoreapplication is not in a pending state (e.g., “managed app—notinstalled”).

At step 246, the control server 110 can determine that the restoreprevention application is not in a pending state, based on the statusresponse. At step 248, the control server 110 can initiatere-installation of the restore prevention application. At step 250, thecontrolled device 120 can re-initialize the restore preventionapplication in a pending state. In particular, at step 260, thecontrolled device 120 and control server 110 can perform correspondingactions described herein with reference to steps 228 through 232 tore-initialize the restore prevention application in the pending state.

With reference to FIGS. 3, 4 and 5, a plurality of flow diagrams areprovided illustrating methods for implementing device management systemwith a restore prevention utility. The methods can be performed usingthe device management system described herein. In embodiments, one ormore computer storage media having computer-executable instructionsembodied thereon that, when executed, by one or more processors, cancause the one or more processors to perform the methods in the devicemanagement system. The device management system 100 includes, amongstother components, a control server (e.g., device management server)having a control server component (e.g., device management manager), acontrolled device (e.g., a mobile device) having an operating systemcleanup utility (e.g., mobile operating system cleanup utility) and acontrolled device component (e.g., device management client application)and a network (e.g., VPN network or public network).

Turning to FIG. 3, a flow diagram is provided that illustrates a method300 for executing implementing a device management system with a restoreprevention utility. Initially at step 310, a device management packageis transmitted to a controlled device to initiate an installationprocess of a restore prevention application. The device managementpackage includes configuration files for configuring device managementon the controlled device. At step 320, a request for an installationfile for the restore prevention application is received. At step 330,based on receiving the request for the installation file, communicationof the installation file is circumvented based on transmitting aresponse code. The response code is an informational code that operatesas an indicator for the controlled device to wait for a final response,the response code is not ignored such that the response code causes anoperating system cleanup utility to not proceed with terminating theinstallation process of the restore prevention application. Transmittingthe response code triggers maintaining a pending state for the restoreprevention application in the installation process at the controlleddevice. The pending state comprises the restore prevention applicationpartially installed at the controlled device, and when the restoreprevention application is partially installed, an operating systemcleanup utility operation to restore default device configurations forarranging application icons on the controlled device, is circumvented,to maintain an existing device configuration for arranging applicationicons on the controlled device.

Turning to FIG. 4, a flow diagram is provided that illustrates a method400 for implementing a device management system with a restoreprevention utility. Initially at step 410, a request for an installationfile for a restore prevention application is received. At step 420,communication of the installation file is circumvented based ontransmitting a response code.

The response code is an informational code that operates as an indicatorfor the controlled device to wait for a final response.

Turning to FIG. 5, a flow diagram is provided that illustrates a method500 for implementing a device management system with a restoreprevention utility. Initially at step 510, one or more installationfiles are for an installation process for a restore preventionapplication. At step 520, a pending state for the installation processof the restore prevention application is maintained. The pending stateincludes the restore prevention application partially installed, inthat, when the restore prevention is only partially installed, anoperating system cleanup utility operation to restore default deviceconfigurations is circumvented based at least in part on a responsecode.

With reference to the device management system 100, embodimentsdescribed herein use a restore prevention application to circumvent anoperating system cleanup utility's capacity to the restore defaultdevice configurations on the device. The device management systemcomponents refer to integrated components that implement devicemanagement. The integrated components refer to the hardware architectureand software framework that support functionality using the devicemanagement system components. The hardware architecture refers tophysical components and interrelationships thereof and the softwareframework refers to software providing functionality that can beimplemented with hardware operated on a device. The end-to-endsoftware-based device management system can operate within the othercomponents to operate computer hardware to provide device managementsystem functionality. As such, the device management system componentscan manage resources and provide services for the device managementsystem functionality. Any other variations and combinations thereof arecontemplated with embodiments of the present invention.

By way of example, the device management system can include an APIlibrary that includes specifications for routines, data structures,object classes, and variables that support the interaction the hardwarearchitecture of the device management system and the software frameworkof the device management system. These APIs include configurationspecifications for the device management system such that the componentstherein can communicate with each other in device management, asdescribed herein.

Having identified various component of the device management system 100,it is noted that any number of components may be employed to achieve thedesired functionality within the scope of the present disclosure.Although the various components of FIG. 1 are shown with lines for thesake of clarity, in reality, delineating various components is not soclear, and metaphorically, the lines may more accurately be grey orfuzzy. Further, although some components of FIG. 1 are depicted assingle components, the depictions are exemplary in nature and in numberand are not to be construed as limiting for all implementations of thepresent disclosure. The device management system 100 functionality canbe further described based on the functionality and features of theabove-listed components.

Other arrangements and elements (e.g., machines, interfaces, functions,orders, and groupings of functions, etc.) can be used in addition to orinstead of those shown, and some elements may be omitted altogether.Further, many of the elements described herein are functional entitiesthat may be implemented as discrete or distributed components or inconjunction with other components, and in any suitable combination andlocation. Various functions described herein as being performed by oneor more entities may be carried out by hardware, firmware, and/orsoftware. For instance, various functions may be carried out by aprocessor executing instructions stored in memory.

Having briefly described an overview of embodiments of the presentinvention, an exemplary operating environment in which embodiments ofthe present invention may be implemented is described below in order toprovide a general context for various aspects of the present invention.Referring initially to FIG. 6 in particular, an exemplary operatingenvironment for implementing embodiments of the present invention isshown and designated generally as computing device 600. Computing device600 is but one example of a suitable computing environment and is notintended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should the computing device 600be interpreted as having any dependency or requirement relating to anyone or combination of components illustrated.

The invention may be described in the general context of computer codeor machine-useable instructions, including computer-executableinstructions such as program modules, being executed by a computer orother machine, such as a personal data assistant or other handhelddevice. Generally, program modules including routines, programs,objects, components, data structures, etc. refer to code that performparticular tasks or implement particular abstract data types. Theinvention may be practiced in a variety of system configurations,including hand-held devices, consumer electronics, general-purposecomputers, more specialty computing devices, etc. The invention may alsobe practiced in distributed computing environments where tasks areperformed by remote-processing devices that are linked through acommunications network.

With reference to FIG. 6, computing device 600 includes a bus 610 thatdirectly or indirectly couples the following devices: memory 612, one ormore processors 614, one or more presentation components 616,input/output ports 618, input/output components 620, and an illustrativepower supply 622. Bus 610 represents what may be one or more busses(such as an address bus, data bus, or combination thereof). Although thevarious blocks of FIG. 6 are shown with lines for the sake of clarity,in reality, delineating various components is not so clear, andmetaphorically, the lines would more accurately be grey and fuzzy. Forexample, one may consider a presentation component such as a displaydevice to be an I/O component. Also, processors have memory. Werecognize that such is the nature of the art, and reiterate that thediagram of FIG. 6 is merely illustrative of an exemplary computingdevice that can be used in connection with one or more embodiments ofthe present invention. Distinction is not made between such categoriesas “workstation,” “server,” “laptop,” “hand-held device,” etc., as allare contemplated within the scope of FIG. 6 and reference to “computingdevice.”

Computing device 600 typically includes a variety of computer-readablemedia. Computer-readable media can be any available media that can beaccessed by computing device 600 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable media may comprise computerstorage media and communication media.

Computer storage media include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by computingdevice 600. Computer storage media excludes signals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer-readablemedia.

Memory 612 includes computer storage media in the form of volatileand/or nonvolatile memory. The memory may be removable, non-removable,or a combination thereof. Exemplary hardware devices include solid-statememory, hard drives, optical-disc drives, etc. Computing device 600includes one or more processors that read data from various entitiessuch as memory 612 or I/O components 620. Presentation component(s) 616present data indications to a user or other device. Exemplarypresentation components include a display device, speaker, printingcomponent, vibrating component, etc.

I/O ports 618 allow computing device 600 to be logically coupled toother devices including I/O components 620, some of which may be builtin. Illustrative components include a microphone, joystick, game pad,satellite dish, scanner, printer, wireless device, etc.

Embodiments described in the paragraphs above may be combined with oneor more of the specifically described alternatives. In particular, anembodiment that is claimed may contain a reference, in the alternative,to more than one other embodiment. The embodiment that is claimed mayspecify a further limitation of the subject matter claimed.

The subject matter of embodiments of the invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

For purposes of this disclosure, the word “including” has the same broadmeaning as the word “comprising,” and the word “accessing” comprises“receiving,” “referencing,” or “retrieving.” Further the word“communicating” has the same broad meaning as the word “receiving,” or“transmitting” facilitated by software or hardware-based buses,receivers, or transmitters” using communication media described herein.Also, the word “initiating” has the same broad meaning as the word“executing or “instructing” where the corresponding action can beperformed to completion or interrupted based on an occurrence of anotheraction. In addition, words such as “a” and “an,” unless otherwiseindicated to the contrary, include the plural as well as the singular.Thus, for example, the constraint of “a feature” is satisfied where oneor more features are present. Also, the term “or” includes theconjunctive, the disjunctive, and both (a or b thus includes either a orb, as well as a and b).

For purposes of a detailed discussion above, embodiments of the presentinvention are described with reference to a distributed computingenvironment; however the distributed computing environment depictedherein is merely exemplary. Components can be configured for performingnovel aspects of embodiments, where the term “configured for” can referto “programmed to” perform particular tasks or implement particularabstract data types using code. Further, while embodiments of thepresent invention may generally refer to the distributed data objectmanagement system and the schematics described herein, it is understoodthat the techniques described may be extended to other implementationcontexts.

Embodiments of the present invention have been described in relation toparticular embodiments which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those of ordinary skill in the art to which thepresent invention pertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects hereinabove set forthtogether with other advantages which are obvious and which are inherentto the structure.

It will be understood that certain features and sub-combinations are ofutility and may be employed without reference to other features orsub-combinations. This is contemplated by and is within the scope of theclaims.

1. One or more computer storage media having computer-executableinstructions embodied thereon that, when executed, by one or moreprocessors, cause the one or more processors to perform a method forimplementing device management with a restore prevention utility, themethod comprising: transmitting a device management package to acontrolled device to initiate an installation process of a restoreprevention application, wherein the device management package comprisesconfiguration files for configuring device management on the controlleddevice; receiving a request for an installation file for the restoreprevention application; based on receiving the request for theinstallation file, circumventing communication of the installation filebased on transmitting a response code, wherein the response code is aninformational code that operates as an indicator for the controlleddevice to wait for a final response, wherein the response code is notignored, such that, the response code causes an operating system cleanuputility to not proceed with terminating the installation process of therestore prevention application, wherein transmitting the response codetriggers maintaining a pending state for the restore preventionapplication in the installation process at the controlled device,wherein the pending state comprises the restore prevention applicationpartially installed at the controlled device, and wherein, when therestore prevention application is partially installed, an operatingsystem cleanup utility operation to restore default deviceconfigurations for arranging application icons on the controlled deviceis circumvented, to maintain an existing device configuration forarranging application icons on the controlled device.
 2. The media ofclaim 1, wherein the installation process of the restore preventionapplication comprises: causing initialization, at the controlled device,of the restore prevention application in the pending state of theinstallation process, using a first portion of an installation packageof the restore prevention application; and processing the request forthe installation file, wherein the installation file is a second portionof the installation package of the restore prevention application. 3.The media of claim 1, the method further comprising: communicating arequest for the controlled device to operate in a restricted mode; andcommunicating a request for the controlled device to terminate operatingin the restricted mode, wherein upon terminating the restricted mode,the operating system cleanup utility operation to restore default deviceconfigurations, on the controlled device, is circumvented when therestore prevention application is in the pending state, wherein thepending state comprises the restore prevention application partiallyinstalled.
 4. The media of claim 3, wherein the restricted modecomprises removing one or more application icons, and wherein theoperating system cleanup utility operation to restore default deviceconfigurations for arranging application icons on the controlled device,is circumvented, to maintain the existing device configuration forarranging application icons on the controlled device.
 5. The media ofclaim 1, the method further comprising: transmitting a status requestfor a status of the restore prevention application on the controlleddevice; receiving a status response of the status of the restoreprevention application on the controlled device; determining that therestore prevention application is not in the pending state on thecontrolled device; and initiating re-installation of the restoreprevention application at the controlled device to partially install therestore prevention application.
 6. The media of claim 1, wherein theresponse code is excluded from a list of response codes that cause theoperating system cleanup utility to proceed with terminating theinstallation process of the restore prevention application on thecontrolled device.
 7. A system for implementing device management with arestore prevention utility, the system comprising: one or more hardwareprocessors; and one or more computer storage media storingcomputer-useable instructions that, when used by the one or morehardware processors, cause the one or more hardware processors toexecute: a control server configured to: receive, from a controlleddevice, a request for an installation file for a restore preventionapplication; based on receiving the request for the installation file,circumvent communication of the installation file based on transmittinga response code, wherein the response code is an informational code thatoperates as an indicator for the controlled device to wait for a finalresponse, wherein the response code is not ignored such that theresponse code causes an operating system cleanup utility to not proceedwith terminating the installation process of the restore preventionapplication; and a restore prevention application agent configured to:process one or more installation files for the installation process forthe restore prevention application; and maintain a pending state for theinstallation process of the restore prevention application, wherein thepending state comprises the restore prevention application partiallyinstalled, wherein, when the restore prevention is partially installed,an operating system cleanup utility operation to restore default deviceconfigurations, on the controlled device, is circumvented.
 8. The systemof claim 7, wherein the control server further comprises a controlserver component configured to: initiate installation of the restoreprevention application on the controlled device; and communicate adevice management package to the controlled device to initiateinstallation of restore prevention application, wherein the devicemanagement package comprises configuration files of configuring devicemanagement on the controlled device.
 9. The system of claim 7, whereinthe installation process of the restore prevention application furthercomprises the control server configured to: cause initialization of therestore prevention application in the pending state using a firstportion of an installation package of the restore preventionapplication; and process a request for the installation file, whereinthe installation file is a second portion of the installation package ofthe restore prevention application.
 10. The system of claim 7, whereinthe control server further comprises a control server componentconfigured to: request the controlled device to operate in restrictedmode; and request the controlled device to terminate operating inrestricted mode, wherein upon terminating the restricted mode, theoperating system cleanup utility operation to restore default deviceconfigurations, on the controlled device, is circumvented when therestore prevention application is in the pending state, wherein thepending state comprises the restore prevention application partiallyinstalled.
 11. The system of claim 10, wherein the restricted modecomprises removing one or more application icons, and wherein theoperating system cleanup utility operation to restore default deviceconfigurations for arranging application icons on the controlled device,is circumvented, to maintain the existing device configuration forarranging application icons on the controlled device.
 12. The system ofclaim 7, wherein the control server further comprises a control servercomponent configured to: transmit a status request for a status of therestore prevention application on the controlled device; receive astatus response of the status of the restore prevention application onthe controlled device; determine that the restore prevention applicationis not in the pending state on the controlled device; and initiatere-installation of the restore prevention application at the controlleddevice to partially install the restore prevention application.
 13. Thesystem of claim 7, wherein the response code is excluded from a list ofresponse codes that cause the operating system cleanup utility toproceed with terminating the installation process of the restoreprevention application on the controlled device.
 14. Acomputer-implemented method for implementing device management with arestore prevention utility, the method comprising: receiving a requestfor an installation file for a restore prevention application; based onreceiving the request for the installation file, circumventingcommunication of the installation file based on transmitting a responsecode, wherein the response code is an informational code that operatesas an indicator for the installation process to wait for a finalresponse, wherein the response code is not ignored such that theresponse code causes an operating system cleanup utility to not proceedwith terminating the installation process of the restore preventionapplication; wherein transmitting the response code triggers maintaininga pending state for the installation process of the restore preventionapplication at the controlled device, wherein the pending statecomprises the restore prevention application partially installed, andwherein, when the restore prevention is partially installed an operatingsystem cleanup utility operation to restore default deviceconfigurations, on the controlled device, is circumvented.
 15. Themethod of claim 14, further comprising: initiating the installationprocess of the restore prevention application on a controlled device;communicating a device management package to the controlled device toinitiate the installation process of the restore prevention application,wherein the device management package comprises configuration files forthe installation process of the restore prevention application.
 16. Themethod of claim 14, wherein the installation process of the restoreprevention application comprises: causing initialization, at acontrolled device, of the restore prevention application in the pendingstate of the installation process using a first portion of aninstallation package of the restore prevention application; andprocessing the request for the installation file, wherein theinstallation file is a second portion of the installation package of therestore prevention application.
 17. The method of claim 14, furthercomprising: communicating a request for a controlled device to operatein a restricted mode; and communicating a request for the controlleddevice to terminate operating in the restricted mode, wherein uponterminating the restricted mode, the operating system cleanup utilityoperation to restore default device configurations, on the controlleddevice, is circumvented when the restore prevention application is inthe pending state, wherein the pending state comprises the restoreprevention application partially installed.
 18. The method of claim 17,wherein the restricted mode comprises removing one or more applicationicons, and wherein the operating system cleanup utility operation torestore default device configurations for arranging application icons onthe controlled device, is circumvented, to maintain the existing deviceconfiguration for arranging application icons on the controlled device.19. The method of claim 14, further comprising transmitting a statusrequest for a status of the restore prevention application on acontrolled device; receiving a status response of the status of therestore prevention application on the controlled device; determiningthat the restore prevention application is not in the pending state onthe controlled device; and initiating re-installation of the restoreprevention application at the controlled device to partially install therestore prevention application.
 20. The method of claim 14, wherein theresponse code is excluded from a list of response codes that cause theoperating system cleanup utility to proceed with terminating theinstallation process of the restore prevention application on thecontrolled device